cc @MCMic

This seems legit as there already is ldap_first_reference, ldap_next_reference, ldap_first_entry, ldap_next_entry and ldap_count_entries.

This is quite off-topic, but I'll try to ask here. Yesterday I was studying the code of openldap and one thing seems little bit inconsistent between OpenLDAP and PHP ext-ldap.

In OpenLDAP the ldapmsg struct is used for all LDAP messages including search result, entry, or reference. No matter, whether a given instance of ldapmsg represents a result, an entry or a reference message, it seems to always work with ldap_{first,next}_{message,entry,reference} as well as with ldap_count_{messages,entries,references}.

In ext-ldap, a PHP resource of type "ldap result" is used for result message and "ldap result entry" for entry or reference. As I understand, we can't pass "ldap result" resource to ldap_next_foo, and we can't pass "ldap result entry" to ldap_first_foo, nor to ldap_count_foo? Also, we're unable to infer from "ldap result entry" resource whether it's an entry or reference. Is there any particular reason for this?

@ptomulik I was not able to email you, I got «550 Denied by policy (in reply to end of DATA command)»

This is quite off-topic, but I'll try to ask here. Yesterday I was studying the code of openldap and one thing seems little bit inconsistent between OpenLDAP and PHP ext-ldap.

In OpenLDAP the ldapmsg struct is used for all LDAP messages including search result, entry, or reference. No matter, whether a given instance of ldapmsg represents a result, an entry or a reference message, it seems to always work with ldap_{first,next}_{message,entry,reference} as well as with ldap_count_{messages,entries,references}.

In ext-ldap, a PHP resource of type "ldap result" is used for result message and "ldap result entry" for entry or reference. As I understand, we can't pass "ldap result" resource to ldap_next_foo, and we can't pass "ldap result entry" to ldap_first_foo, nor to ldap_count_foo? Also, we're unable to infer from "ldap result entry" resource whether it's an entry or reference. Is there any particular reason for this?

I guess the original authors of php-ldap thought it wiser to differentiate between an operation result and an entry, it seems convenient to me.

About inferring whether it’s an entry or a reference, what’s the use case here? You should now what you asked for (entry or reference), no?

@ptomulik I was not able to email you, I got «550 Denied by policy (in reply to end of DATA command)»

Well, that's McAfee :)

This is quite off-topic, but I'll try to ask here. Yesterday I was studying the code of openldap and one thing seems little bit inconsistent between OpenLDAP and PHP ext-ldap.
In OpenLDAP the ldapmsg struct is used for all LDAP messages including search result, entry, or reference. No matter, whether a given instance of ldapmsg represents a result, an entry or a reference message, it seems to always work with ldap_{first,next}_{message,entry,reference} as well as with ldap_count_{messages,entries,references}.
In ext-ldap, a PHP resource of type "ldap result" is used for result message and "ldap result entry" for entry or reference. As I understand, we can't pass "ldap result" resource to ldap_next_foo, and we can't pass "ldap result entry" to ldap_first_foo, nor to ldap_count_foo? Also, we're unable to infer from "ldap result entry" resource whether it's an entry or reference. Is there any particular reason for this?

I guess the original authors of php-ldap thought it wiser to differentiate between an operation result and an entry, it seems convenient to me.

About inferring whether it’s an entry or a reference, what’s the use case here? You should now what you asked for (entry or reference), no?

ldap result entry resources for entries and references are not fully interchangeable. For example ldap_parse_reference() will always fail (actually return false) for a true entry resource without any error information. If a resource is provided as an argument to my function (e.g. function __construct($ldapResultResource)), I'm not able to fully validate it in front with is_resource() + get_resource_type(). There also is no php-ldap API for that (openldap seems to provide ldap_msgtype() for that). So, for example debugging gets a little bit harder.